 Prev Next  |
Print
Publishing can involve the entire Sitecore Master database, such as when choosing Publishing > Publish in Content Editor, or a specific Item or branch, such as when choosing Publishing > Publish Item. In the first case publishing starts from the root of the content repository; in the second publishing starts from the selected item.
When changes are made to any items not associated with any workflow in the XML repository through the CMS user interfaces, Sitecore adds those items to an internal publishing queue. When items associated with workflow reach a final workflow state they are added to the publishing queue. Incremental Publishing operations publish all items in the queue, copying the appropriate versions of the appropriate items from the master to the web database.
Incremental Publishing transfers all approved and system updates to result in a published website consistent with these records in the master database. Smart Publish and Republish, which do not use the Publishing Queue, synchronize a target database with the appropriate data from the master database. Incremental publishing usually consumes less time and machine resources than Smart Publish. Republish is the most expensive type of publishing as expired versions must be deleted and the cache must be cleared. The Publish Item command may publish an individual item instead of recursing the repository depending on user selection.
Smart publishing compares the appropriate language versions and publishes only the items which have changed since their last publication, starting with the root item and recursing the content repository. Every change through the Sitecore UIs causes a new internal revision identifier to be assigned to the item (note that this identifier has nothing to do with the Sitecore version identifier used for version comparison, reversion, etc.). Smart publishing compares each item’s internal revision identifier in the master database with the corresponding identifier in the web database and publishes only those items for which the identifiers differ.
Republishing will overwrite every item in the target database with appropriate data from the master database, even if that data has not changed, and only Republish will remove obsolete versions from the target database. Republish is intended for cases such as:
- Bringing a new web database online
- Restoring a backup of the master database
- When Publishing or Staging is interrupted due to network conditions
- Adding a new content language, publishing target or other relevant system item
Prev Next